nick timer warnings may be sent with unexpected target

[slingamn]

(11:54:27 AM) bogdomania: dan-:
(11:55:09 AM) bogdomania:  "This nickname is reserved. Please login within 30s (using /msg NickServ IDENTIFY <password> or SASL)"
(11:55:19 AM) bogdomania: Nick is reserved and authentication timeout expired: 30s
(11:55:44 AM) bogdomania: which is legit.. but, if I change back the nickname,
(11:56:09 AM) bogdomania: the 30s countdown timer starts, and the nickname is changed again
(11:56:25 AM) bogdomania: except, the 2nd time I don't get a warning message, like prior
(11:56:30 AM) bogdomania: is this ok?

(05:52:01 PM) slingamn: interesting
(05:54:55 PM) slingamn: i can't reproduce this
(05:55:00 PM) slingamn: i get a warning every time
(05:55:09 PM) slingamn: oh hmmmmmmm
(05:55:15 PM) slingamn: the warning comes in before the NICK line
(05:55:35 PM) slingamn: so the client may not display it correctly because the target is unexpected

[slingamn]

The fix is probably to supply the ResponseBuffer as an optional (nil-able) argument to NickTimer.Touch()