I know that the .NET CLR team adjusted its behavior to address this scenario, fwiw!