All this about menu-logging being "cheating" when FD have explicitly said it isn't. I don't do it, I think it's lame, but it isn't cheating the way task kills or network kills are. There's actually a relatively simple solution to it too. FD just need to make a menu disconnect completely indistinguishable from high-waking out. During the 15sec cooldown, others see the hardpoints retract, detect a surge and when the timer expires drop a high wake to a randomly selected nearby system. If they follow it, they won't find the ship they were chasing, but that's easy to achieve for pilots that don't disconnect anyway. Give the attackers absolutely nothing - no visual differences, nothing in their client logs, nothing at all - that lets them tell whether their target exited the game gracefully or high-waked elsewhere and successfully lost themselves. That way the entirely justifiable ire at combat-loggers can remain where it's deserved, aimed at the people who actually ARE cheating.