The product owner wants to keep track on how much points are spent on bugs during a sprint. This can raise some issues, such as:
Scoring a task that is already done. Surprisingly even with it done, there are sometimes discussion and divergences.
Scoring many small tasks with 0 points that at the end actually sum up to something meaningful (a bunch of fast fixes).
Counting points spent on bugs as available points for new features in the next sprint, alongside with new bugs that eventually will show up.
I agree with him that it is important to track the time spent on it, but points doesn't seems to play really well in this case. So what are the best approaches and practices in this case? Count the hours spent on each one?