Neat stuff! I've experimented a bit with the analysis features of VS but only through the one provided with the Xbox 360 SDK, I'll make a point of checking out VS2012's even if it is more crash-prone.
Does the application verifier move all allocations, especially those made through C/C++ heap allocation functions, to page boundaries or just those made with HeapAlloc et al? I've had good luck with valgrind on both Linux and OS X for diving into difficult bugs and shining a light on what may eventually be a problem.
App Verifier just moves HeapAlloc allocations, but the C/C++ functions default to using these, so it grabs pretty much everything.
For game development I wrote a custom allocator that redirects all of our allocations to the Windows heap instead of using our custom allocator, in order to support App Verifier and xperf memory profiling.
It's not similar to valgrind. It's more like Electric Fence.
Does the application verifier move all allocations, especially those made through C/C++ heap allocation functions, to page boundaries or just those made with HeapAlloc et al? I've had good luck with valgrind on both Linux and OS X for diving into difficult bugs and shining a light on what may eventually be a problem.