You're not a moron - at least not because of this mistake :)
I've seen it happen many times. Developers will find a bug in their code
and try to debug it by listing properties in a watch window, but then
completely forget about them. Then, they report all sorts of weird behavior
that they think is related to the original bug. One indication of this
might be when they say, "I can't reproduce the problem in the de *** ".
Right, because of the observer effect - as soon as you attach to the process
you're changing it.
This is something that all developers should be aware of when using the
de *** . One way this issue can be alleviated is to make sure that
properties don't change internal state or call methods in their get
accessors except for when lazy initialization is desirable for the backing