The whole point I, and others, are making with the deterministic solution is that you CAN do something about it, i.e. allow for the use of a deterministic rounding function. :P
Only in combination with 0% luck (if you only ever use low numbers of armies a few percent of luck would also work). Even with deterministic rounding, at some point you'll need to have a "cut-off" between rounding up or rounding down. You can put it anywhere you want, but unless you use 0% luck, the attack might still end up killing either just below or just above that cut-off point.
Do keep in mind that if you do this, it might be possible (I don't have a proof or example, just a gut instinct and not nearly enough motivation to look for an example :p ) that you could "trick" the average offence kill ratio to be higher than the average defence kill ratio. (This is most likely to be possible when you mainly perform attacks with very low numbers of armies.) This also seems undesirable.
Maybe you don't yet understand the significance of having your spares well placed.
I was trying to explain it wasn't talking about any other considerations, only about the chance of a successful attack. And in that case, the difference between 3vs2 and 4vs2 is the same as between 3vs2 and 3000vs2: none at all.
The wiki presents the two functions the (random rounding and straight rounding) as alternatives. In the same paragraph it suggests that the random function is important because the deterministic function has problems. To make such a case assumes that there must be mutual exclusivity in their implementation, because if they could coexist, then you cannot use a disadvantage of one to justy the use of another.
The Wiki is not proposing Monkey's solution, Monkey is! I agree with the Wiki that straight rounding has downsides. I also think Monkey's alternative has those same downsides (albeit less severe, since in a very real way it's a compromise between the current system and straight-rounding).
Okay, so if we take the parameter of Monkey's approach and set it to 1, we have the current situation. If we set it very high it becomes very close to straight rounding (in fact, if we'd set it at positive infinity, it actually is straight rounding). But since it kind of make a whole lot of sense that properties change when a parameter changes, I fail to see how this would imply a "mutual exclusivity in their implementation" (to be fair though, I'm not entirely sure what that even is...).
And maybe the most important point:
Even though I don't like Monkey's solution, disagree the situation he wants to solve is a problem in the first place and am unlikely to use this even if it were implemented,
I do think his mathematics checks out, it would solve the "problem" (if you think there is one) and it is probably feasible to implement.
I may not like Monkey's idea, but I do not think it's a bad idea (which is an entirely different and near-unrelated matter).
If you go back, you will notice that once I correctly understood what Monkey is proposing (this post), I stopped objecting to it, even pointing out that the option to use a parameter to keep the current situation is a good thing. (Just about everything I posted in this thread after that is to explain the Wiki is not "blatantly wrong".)