I was working off of this text from the documentation:
BlockInput Compared to SendInput/SendPlay: Although the BlockInput command can be used to prevent any keystrokes physically typed by the user from disrupting the flow of simulated keystrokes, it is often better to use SendInput or SendPlay so that keystrokes and mouse clicks become uninterruptible. This is because unlike BlockInput, SendInput/Play does not discard what the user types during the send; instead, such keystrokes are buffered and sent afterward.
I was under the impression that the purpose of SendInput was to stop (actually buffer) keys (and I assumed mouse clicks) from effecting the sent text, which was not happening. It seemed like the intent of the programmers was for SendInput NOT to be interupted by a ControlClick command, thus I felt it was a bug.
No worries either way, though, as I have a script that works and makes my job much easier and, thus, I am thankful for that.
Gibbons