C is fundamentally not designed to make avoiding them possible
A software engineer says, "Yes, I've developed techniques for avoiding entire classes of bugs in C, but there are a few types I'm still struggling with."
Someone who has not yet developed the engineering mindset immediately comes up with excuses. "We can't do that."
An engineer looks for solutions, not excuses. It's easy to tell the difference once you recognize it.
What you're describing is "a truly random number generator with a uniform distribution of outcomes"
Apparently it's also called perfect randomness.
I skimmed a few of the referenced papers back to something in 1986.
It turns out that the practical implementation of a theoretical perfect (quantum) random bit generator (the example given in one paper was a zener diode[1]) always has some skew. This might vary over time but, for example, a random bit stream that is biased to more ones than zeros over the last 10s is more likely than not suffering from some temporary bias that an attacker can at least theoretically use.
Using classical physics it's possible to remove this bias so that you have a pseudo-random stream that is, for all practical purposes perfect however it's (apparently[2]) provable that doing this in the classical domain is theoretically open to attack due to the original bias.
What this has done is allowed a quantum process to do that post filtering so that even the theoretical attack on the pseudo-random stream driven from an almost perfect RNG is gone.
[1] example here - different paper:
https://www.researchgate.net/f...
[2] I took it on trust - one paper said it was proved in another referenced paper, I didn't try to check if it really did say that and I certainly didn't even try to follow a proof...
FORTRAN is for pipe stress freaks and crystallography weenies.