Microsoft have confirmed the issue I've described is a bug, and it will be fixed in the first service pack of SQL 2012. Hotfixes for previous versions of SQL can be obtained from Microsoft. Please see Connect ID 737342.
Thanks to all for your suggestions and advice.
↧