I'm sorry for the awfully slow response to this thread.
Obviously, some time has passed since you posted this issue, and the 1.0.2 patch has since been released as well. Are you still seeing this issue? I have not been able to reproduce it so far.
Please let me know!
Thanks,
Steve