I installed Inspector XE and VTune XE over VS 2008 to check them out.
For Inspector XE and VTune XE :
User interface is not very user friendly lots of fudging around to set up the file to process when in standalone mode. Lots of repeats to tell it where to find things. Does not remember previous choices need to restart at root of system.
Not possible to define subset as to what is to be inspected on large projects previous versions had a configuration utility which enabled a subset of the entire application to be selected. The only response to this issue is in Inspector (but not in VTune) Modules to exclude but there is no list such as in the previous version they must be expressly typed in.
Results on using Inspector XE
With a simple Open MP for loop missing a reduction and private attributes it does not find the data races.
If I remove the data race condition, then it finds the simultaneous use of a non reentrant library function but it reports it as a data race problem.
It reports a very cryptic stack cross access condition which remains unexplained.
I found the need to redefine things on successive runs, such as the location of source files.
Thread Checker no longer runs properly I get a call support type error.
The app being Inspector XEed contained User Event API Functions - coud these pose a problem and are they supported in the new XE products?
Inspector seems pretty close to Thread Checker however its non detection of blatant OMP data races needs explaining.
This is after spending an afternoon on the two products I may have missed a lot of issues or may be simply reacting negatively to lots of changes. Iy would be interesting to get other user feedbacks.
I have similar comments on rh VTune XE forum.