Unfortunately, we were not able to find a workaround for this issue. However, the development team has managed to resolve this problem. The fix will be delivered with the next internal build, as well as the forthcoming 2013 Q1 Service Pack.
Please, excuse us for the inconvenience. Don't hesitate to contact us if you have other questions.