Do you know how to laser in on the smelliest code?
Rather than randomly browsing for dodgy code, use Visual Studio's Code Metrics feature to identify "Hot Spots" that require investigation.
Identifying the problem areas is only the start of the process. From here, you should speak to the developers responsible for this dodgy code. There might be good reasons why they haven't invested time on this.
Tip: To learn how to use Annotate, see Do you know the benefits of Source Control?
Suggestion to Microsoft: allow us to visualize the developers responsible for the bad code (currently and historically) using CodeLens.