This is going to be tricky. And all seemed to work perfectly. Sigh. Windows timers only have milisecond resolution (and very bad at that) so os.clock is a no-go on it. SysTime seemed to work but seems to just get massive time jumps randomly. On Linux (and I suppose Mac OSX) this works better. SysTime seems to have the same time jumps but less frequently and os.clock seems to work great and has a few microseconds resolution (which is good). As such, os.clock is the default on Linux.

To time or not to time, that is the question. Basically, either find a workaround on Windows or count operations. The idea is, each function has a set ops cost and each Lua op counts as one(?) LuaChip op. So, each time debug hooks are called, add their "count" value to the total ops consumed. I feel dirty...

When stopping coroutines (if they spent too much time executing) while they were calling a Lua C function that, for example, makes a hook.Call like Player:Kill, can create errors inside those hooks and there's no way for the debug hook to know this (besides using expensive debug.getinfo). Maybe remove the debug hook on calling certain C functions and replace it later?