@Duncanma: This is now fixed...

http://msdn.microsoft.com/en-us/library/ms189275(SQL.105).aspx