If anyone tries it, let me know how it works. If you find issues that are not on this list, please send me a note describing the details of the problem, what environment you're running under, and the symptoms seed. Everything returns to normal. An attribute path can be non-unique, making the value displayed in the watches window unpredictable. I haven't thought too much about how to make the production for the watch more specific so it only fires on the specific attribute selected in the StateMap.
Breaks act wierd.
Statemap collapses on an update. Because the entire tree can change from one update to the next, it is collapsed and completely redrawn, rather than changing only those items the user has expanded. This can probably be changed in a future version. The debugger windows don't refresh in expected ways in Windows as they do under Linux. This is a matter of taste.