The problem is that the Date data type is misleading and makes you think it is helpful. It is sometimes, but not in the way you wanted it to be for this particular problem.
You will need to continue to use a function when the times you are tracking are not date/time elements. In this case, what you describe is a resource like kilograms/pounds, dollars/euros, liters/quarts, etc. I.e. things that have an integer part and a fractional part.
When you add up hours and fractions like that, you are not using Access "native" Date/Time information. Native time format is days and fractions of a day, expressed as a Double (64-bit floating) number, since midnight of the reference date. For Windows, I believe the reference date is 1-Jan-1900, but don't make book on it. If I got it right, then midnight of 1-Jan-2000 was something like 36524.00. I've also heard of a 1-Jan-1970 reference but cannot recall the context. It might be some other application that uses the more recent number.
Because you aren't using "native" time format, none of the normal date/time functions will work correctly. Be prepared to "roll your own."