Now I would like to thank MoonShadow and Rudd-O for answering my question, and koin for his counterquestion which actually seemed interesting but that everyone ignored...if it really is true that...
If a bit-sifted address is developed and recognized by the protocol, the block reward would be able to continue to bit-shift the block reward for another 24+ bits.
...then
I consider my question to be answered (although I would like to learn more about the "+" in "24+", and about how impossible it would be to use koin's idea).
While I can't verify my own statements, I was not ignoring your question. It's just not one that can be easily answered by the vast majority of the forum membership. Only the developers can respond to my claims, for or against, with any certainty; and most of them don't much participate in the forums.
But let me qualify that, while it's a bit more complicated than even I implied, that is basicly the solution posed by others in the past when this kind of issue has come up. I'm fairly certain that it's all but decided that such an address type is to be developed, but it's just so far down the priority list (being decades away from need) that it's pretty much ignored. For additional detail, let me describe how a transaction stores coin value into an address.
Technnically, bitcoins don't actually exist, even as a digital construct. This is a concept that tripped me up early on, but there is no text file, digital object, or portion of any transaction that we could point to and say "that's a bitcoin"; like we could open up a filesystem and highlight a file and say "that's an email" or "that's an MP3 song". The concept of the coins themselves is
entirely an abstract idea. How it works is; the blockchain works like a huge, massively replicated, distributed LETS ledger containing only details of transactions from one or more addresses to another set of one or more addresses. The varialbes that are used to contain the values that are transfered in these transactions are 64 bit integer values, which contain no decimal points. As a matter of convention, Satoshi established that the clients should display those totaled values with a decimal point in the middle of those 64 bits (32 bits form the value shown to the left of the decimal point, 32 bits show the value to the right of the decimal point). Said another way, the protocol has no concept of BTC's, but only deals in satoshis; but humans have a problem with dealing with numbers quite so huge, and this is why teh clients display the totaled values the way that they do, resulting in the (technically false) meme that there will only 21 million currency units. However you choose to look at it, the bits of those interger variables with the greatest values will never be used, because the entire monetary base can be stored into a single 64 bit integer using only 48 bits, as the actuall 21 M BTC in binary would look like this...
(111,011,101,011,111,000,001,011,010,000,001,110,100,000,000,000,000)
So there are 16 bits (or so) to the big end available to place a binary token, that would tell the clients & miners that this address value isn't in the standard "whole" satoshis, but instead expressed as a more fine value, say with a decimal point in the middle (of the 48 bits in use) thus permitting the protocol to advance the coinbase division to another 24 bits of fractional satoshi units.