Hi, thanks for posting!
Although this behaviour is not ideal at all, it is, quite sadly, the best approach available given the design of NCrunch.
NCrunch's analysis and test discovery is all entirely post-build, which means that its ability to navigate to tests is constrained by the debugging information output by the compiler. This is very different to tools such as CodeRush and Resharper, which pre-compile code and can therefore have access to information about the specific locations of tests along with their structure.
Where a test is derived from a class and not a method (as is the case with normal fixture tests, or MSpec behaviors), NCrunch has no reliable debugging information to mark the location of the class within your source code - hence there is no navigation target available.
I'm sorry, I wish I could say that it was possible to fix this, but to do so would require massive amounts of new development (i.e it would basically be like turning NCrunch into a refactoring tool).
Cheers,
Remco