Back in the real world though, UTF-16 almost never "wins" size comparisons in practice. For example, one would think that UTF-16 would be "better" than UTF-8 for pure Thai documents (2 bytes vs 3 bytes per Thai character) but in reality such a comparison is irrelevant, since the Thai government have decided that both are unacceptable in most cases and instead mandate the use of TIS-620 (1 byte per ASCII or Thai character).
It's a similar story in almost every other case where UTF-16 may seem like the best choice for size purposes. There's usually a specialist or national standard encoding in place, with much more traction (and often required by law), that is smaller and doesn't share any of the heinous issues suffered by UTF-16.
tl;dr: I don't think you made the point strongly enough. UTF-16 is an absolute joke and will only stay around due to Microsoft's stubbornness and lack of foresight. If you voluntarily use UTF-16 in 2014, you are a moron.
Your understanding is incorrect and the option to "delete" an account hasn't existed for a long time. You might want to check these things next time, since the only thing your comment is likely to do is mislead people and waste their time looking for something that isn't there.
The only reason Objective-C is not a relic of the past is that Apple are stuck with it. Some people mistake this relationship and think ObjC isn't a piece of shit. Poor fools.