Hi,
I've been having this idea to create my own cycle counter and just yesterday I've realised that Hatari can do that for me with nearly zero effort. :)
The idea is that you have a m68k code in memory, disassemble it and you see not only each instruction's size but also cycles it eats. And since it would be in Hatari, you could immediately calculate whether it's a cache hit/miss, influence of the instruction head/tail, literally anything needed.
Since Hatari already tries to calculate Falcon's bus activity and CPU cycles, how hard this would be? Virtually just one more column with the cycles number and some indication about instr/data cache state.
--