It's a ridiculous thing to worry about in either of your cases. That incredibly specific situation simply isn't ever going to happen in practice because so many other conditions need to be met for the compiler to let you proceed.
Not necessarily at all.
> unless the only thing you ever do to that object is call fire(), which is nonsensical
You can be calling other methods on the object in other places, but in one particular block of code you may be only calling fire(). And in that block of code, all the compiler cares is that the type has a fire() method. Thus the compiler is not doing a full check.
> It's a ridiculous thing to worry about in either of your cases.
Not at all... if your program is running inside a NASA rover, or if your program is running inside a robotic surgery machine you have to worry about safety and you want to maximize compile-time checks.