It is a good analogy. You are right! However, the general public knows about antilock brakes. They use them every day. Just as most divers use computers these days. For those who need special skills, such as law enforcement agencies doing special manuvers when driving the same can be said for Tech divers needing special skills needing more indepth information regarding decompression theory and the tables. I know how antilock brakes basically work but not all the details. I know how the tables basically work but not all the details....
Where the analogy probably comes up short is that if the anti-lock features of the brakes fail, you at least still have brakes and they still more or less work the same way (push the pedal down and the car slows down).
What happens when a dive computer fails however? If it just shuts down it is obvious and you immediately ascend, do a safety stop and stop diving.
But what if the depth sensor is off or the computer is producing faulty deco information? That requires some knowlege, resources and problem solving skills, or at least enough knowledge of the conditions, site, tables and planned dive schedule to figure out the worst case scenario and do a sufficent safety stop to cover that eventuality. A buddy makes it relatively easy if you can compare computers and figure out which one is clearly wrong, but you need some basic information and pronblem solving skills to determine that.
Even in the abscence of a buddy (let's assume aliens abducted the buddy) if the diver listened to the briefing and knows the max depth of the site, he or she can estimate his or her average depth and using familiarity with their own SAC can estimate max dive time, even if he/she does not have a dive watch. Add to that some basic table knowledge (for example knowing that with your normal SAC that you can't exceed the NDL's above a max depth of X feet on the first dive of the day on an AL 80, knowing that a 5 minute stop at 10-15' will cover any deco I could get into on the second dive with an AL 80 down to X feet of depth) and the diver will have a pretty good idea how long to stay at a safety stop to ensure a safe ascent.
Teaching some basic table knowledge and some basic contingency planning will better prepare the diver for a computer failure. If you don't teach that, would you teach the diver to carry a redundant cmputer?
Consider another type of less obvious computer failure:
A decade or so ago, I was tooling along at 100' with an air integrated computer and noted I had 1870 psi left, which struck me as being a bit more than I expected based on 15 years of diving and familiarity with what I should have based on time, depth and SAC rate. So I checked 2 minutes later and had the same 1870 psi left, so I immedately aborted the dive and surfaced. It turns out the Uwatec quick disconnect had a sweet spot where it could come unscrewed just enough to trap the gas in the HP hose without venting it, so you got a pressure reading, but one that never changed.
Had I simply relied on the computer's faulty information and not validated that information with other knowledge and information (knowing what to expect for a reading, noticing when the reading I got deviated and noticing again that the reading had not changed - a potenail issue for some divers at 100' END) I potentially could have gone OOA later in what was planned to be a much longer multi-level dive.
So again, a diver does not have to know the intimate working details of a dive computer, but they do have to understand the basic operating principles and the potential failure modes.
As Howard states, a basic understanding of how tables work is part of the knowledge a diver needs to know to dive a computer safely rather than just being overly reliant on it.