It is good to be reminded of the horrors of C++. I'm happy to be working with C# and have Resharper enabled. It easily catches all of the bugs in this test.
Accord.Net - http://www.viva64.com/en/b/0410/
Microsoft WPF Examples - http://www.viva64.com/en/b/0407/
Xamarin.Forms - http://www.viva64.com/en/b/0400/
Lucene.Net - http://www.viva64.com/en/b/0381/
Xenko Game Engine - http://www.viva64.com/en/b/0379/
Space Engineers - http://www.viva64.com/en/b/0376/
WPF examples by the Infragistics Company - http://www.viva64.com/en/b/0375/
CNTK tool kit - http://www.viva64.com/en/b/0372/
Sony C#/.NET component - http://www.viva64.com/en/b/0371/
IronPython and IronRuby - http://www.viva64.com/en/b/0367/
MonoDevelop - http://www.viva64.com/en/b/0366/
CoreFX - http://www.viva64.com/en/b/0365/
Roslyn - http://www.viva64.com/en/b/0363/
Still, in reality, knowing that your code has a bug is just one part of the story. Having huge legacy code base usually means you've got to fix the bugs as you go about your business implementing features/fixing other bugs. You cannot simply spend a year fixing bugs no-one actually cares about (because software was working well enough before).
So in this drive-by scenario IDE-integrated tool is much more useful than some offline report-generating tool. You see a warning live in your editor - you fix the issue - you move on. Very low effort and effective in the long run.
You can easy try PVS-Studio. Explanation about the PVS-Studio demo-version limitations: http://www.viva64.com/en/b/0395/
> You cannot simply spend a year fixing bugs no-one actually cares about (because software was working well enough before).
Yes. You can analysis only newly written code. Best Practices of using PVS-Studio. Now with C# support: http://www.viva64.com/en/b/0364/