I haven't counted how often the Windows code uses a

W

(unicode string) API and then does a corresponding

wstringToString

conversion step afterward when it could have just called the corresponding

A

API in the first place (ansi string), but, is there a reason for that?