http://blogs.msdn.com/b/cellfish/archive/2008/11/18/dangers-of-using-visual-studio-2008-team-system-code-coverage-tool-for-native-c.aspxSo now you know how to get coverage reports for native C++ using Visual Studio 2008 Team System (if not - read this ). There are a few things you need to know before you get excited. First of all the only metrics you get are line and block coverage. Aen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/cellfish/archive/2008/11/18/dangers-of-using-visual-studio-2008-team-system-code-coverage-tool-for-native-c.aspx#9572872Tue, 28 Apr 2009 06:38:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:9572872Being Cellfish<p>I've previously recommended Bullseye . And there is another nifty feature with Bullseye you should know;</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9572872" width="1" height="1">http://blogs.msdn.com/b/cellfish/archive/2008/11/18/dangers-of-using-visual-studio-2008-team-system-code-coverage-tool-for-native-c.aspx#9137345Mon, 24 Nov 2008 17:44:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:9137345Team System News<p>Cellfish on Dangers Of Using Visual Studio 2008 Team System Code Coverage Tool for Native C++ Jason...</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9137345" width="1" height="1">