This has been the case ever since the pause feature was introduced.
Not a fix, but if you have the Parity Check Tuning plugin installed it ‘patches’ the history entry to give the correct details for the whole of the run (as well as providing some other features you may find useful). Having said that I perhaps need to check that this is always the case when manual pause/resumes have been done rather than automated ones. I think it is handled properly but I am not 100% sure.