The generic destroy would work fine, since the class would remember all the fields it generated using this syntax just as well as it could using any other syntax.

I agree that this still names the field twice (public name optional, internal ref optional) when most of the time you'd be happy to use the same name in both places.