Ahh, I got it. So yeah, I guess that would work -- mIRC sees the already-resolved address and calls for a socket to that address, which Windows fulfills and gives back to mIRC. What mIRC doesn't know though is that Tor has already mentioned to Windows that 192.0.2.2 is a synonym for 127.0.0.1, so Windows connected the socket mIRC asked for to 127.0.0.1:9150 and not 192.0.2.2/6667 like mIRC thought.Then Tor does it's usual thing, all while mIRC is unaware it isn't connecting directly to whatever wherever. Neat. Seems like the same thing as torify or socksify does, basically, but still neat that Tor has the feature written in natively.