I think that very strict time tracking doesn't worth. Strict time tracking means that you count the hour halves or lower you spent on a particular task. Strict counting will take some time, which adds up. Eventually, you'll spent a significant amount of time on tracking the time than doing what you're supposed to do.
When estimating a task, the estimations should contain real time, not ideal time. Real time includes small interruptions and other "human related" factors.
A more relaxed tracking will introduce some errors for a tracked task (if you record one hour for a task, and the real time spent is 50 minutes, you'll have a difference of -10 minutes), but overall, if you summarize, the errors compensate.
If you need to use the tracked time to improve your efficiency and performance, it doesn't matter too much that for a small task you spent 5 minutes more or less. What it matters is that the overall difference between the estimation and the actual work is not too much.
Later edit
If you need to use the tracked time to justify your activities on the project, I used to proceed in a different way. I wrote down the significant, "non-obvious" activities (various meetings, administrative stuff, team discussions, coaching, etc.) that I had to do on the project, and made a separate tracking for those activites.