> The Swift code is compiled and executed, assuming all the corresponding overhead.

Unless it's cashed, of course, then you get the extra overhead on first run, but lower overhead on at the subsequent runs? This is even mentioned in the article, so what's the issue in this specific peculiarity?