None of the altimeters included with a cyclecomputer are going to be aviation-accurate, which is what you are talking about. I have two on my bike at the moment (Polar s720i and Ciclo 434m), and they always show some discrepancy, although typically it is minimal enough that it doesn't matter (75-200'😉.
As for people saying "mine always requires recalibration, so it's a pain"... well, welcome to the world of barometric altimetry. That's why pilots have to update their altimeters while flying, because pressure is typically changing, especially if you travel large distances (which we, as cyclists, tend not to do). The amount of pressure change during a typical ride isn't so significant (maybe changing the altitude by 100-200 feet); that's why often your altitude is different at the start/end of a ride. If you happen to ride during the time that a weather front is passing your location, it can be more extreme than this, but your ride wouldn't likely be much fun!
If your instrument is in the house, then you take it out to ride, the temperature variation is going to throw it off a bit, even though most state they adjust for temperature fluctuations.
Unless you want to know the best approximate of your current altitude while riding, it's completely unnecessary to 'calibrate' your altimeter in order to get accurate climb data. The ascent in feet is going to be the same whether it's calibrated or not.
As far as showing an ascent during a flat ride, this could be due to both pressure and temperature fluctuations, as well as the simple accuracy of your instrument. There are few 'completely flat' courses out there; I sure wish I had one around me for flat time-trialing.
I think that altimeters are very handy tools that represent the difficulty of a ride MUCH more accurately than just looking at mileage. I'm still constantly befuddled by how training programs and 'coaching tips' neglect actually quantifying climbs during riding, as it directly effects both your effort and your average speed.