I don't think `@:allow` has problem with overrides either, but we can't change the scope of a function in overrides (like for `destroy()`, which is `public` in `FlxPoint`).

I think the allow+private-solution is actually preferable, because it doesn't just hide the functions (which also only works if you use compiler completion in FD).