1. Not a bug - Construct 2 uses high resolution timers where available (which would have microsecond precision), and by default only runs at 60 FPS (every 16 ms), which means you cannot rely on the timer ever reading an exact value. This is not an issue with C2, it's just a general game design point you have to deal with when using any technology.
2. I don't understand this problem. What is the 'g' key? Please be sure to clearly report exactly how to reproduce the problem, what you observe happen, and what you expected to happen instead. Be sure to also remove any events not relevant to the problem. It would be useful to create separate .capx files for each individual problem you want to report.