The issue is no longer reproduced in UI for WinForms. The fix was included in our suite with R1 2012 SP1 version (2012.1.321).