This is something that I've seen from time to time in VS.NET with both Measurement Studio and non-Measurement Studio components. I'm not sure if it's a known bug or not, but Measurement Studio components have no control over this and this would be an issue with VS.NET, not Measurement Studio. Anytime I've run into this problem, I just restarted VS.NET and the problem went away.
- Elton