Interesting observations, hrothgar1!
I should be more precise of what I meant by Par-N-Rar succeeded where ABZ failed: As you noted, hrothgar1, Par-N-Rar basically uses the par2commandline routines, and, hence, it also misses some good blocks every now and then. What I like about it, though, is that the program indicates the correct number of blocks that is needed for its repair function to work smoothly.
As far as I can tell, that's where the problem with ABZ lies: Its checking algorithm (like Quickpar?) to identify missing blocks is more advanced than the actual repair routine. Therefore, occasionally ABZ downloads too few blocks for the repair to work. Now, my point is that if ABZ used the same (although inferior) checking routine as par2cmdline uses, there shouldn't be any failed par processes anymore.