@elschmitt: you can use incognito mode to test your changes as it won't have remembered anything.
A trick we use when forcing changes to sites in production is adding a query string to the url from a page that is referencing the file that effectively does nothing, however, it is a signal for chrome to reload it.
e.g. <script src="~/public/js/my-file.js?v=1.1"></script>
If a change is made to my-file.js and we need to be absolutely sure the user gets the change and might not reload their cache it becomes <script src="~/public/js/my-file.js?v=1.2"></script> which as far as Chrome is concerned is a different file.
It is a shame this is only available in ultimate. This feature would be worth paying for as a plugin for visual studio professional. Have you ever thought of having an app store for development tool extensions within Visual Studio?