NUnit stacktrace messed up

NUnit stacktrace messed up

When using NCover Console to profile a set of NUnit tests, it seems that NCover influences the line numbers of failing NUnit tests.

The line numbers of failing tests are different when running the test with or without NCover. The numbers seem to be off by 1 when running with NCover. Because we also use the Shouldly framework in our test code, this severely affects the NUnit error output.

Did anyone else experience this type of problems?