VSM Strangeness

While migrating a Silverlight 2 Beta 1 control to Beta 2, I encountered some odd behavior with the VisualStateManager and I thought I would document my experience in the event that you might run into the same issue. From what I can tell, this only occurs when you have multiple instances of a control that change state by animating color properties (ColorAnimation). There may be other ways to induce this behavior, but the following is the only way I have encountered personally. Simply put, calling VisualStateManager.GoToState to does not always go to the correct state in some cases, even though no exception is thrown and a true boolean value is returned.