This annoyed me pretty much ever since we got the watch window, and I know it's too late to complain, but maybe someone knows a workaround.

In the debugger, if I set a watch on an expression, is there a way that expression going in and out of scope would NOT count as a change?

For example, I'm looking at contents of a field; the field becomes "can not be evaluated" every time execution goes to default datasession (framework code is instantiated there). Having a breakpoint on that becomes unusable.