You will get a much better response if you improve your questions. Here is how you can improve your questions: 1) Show us the code. You already do this. Good. 2) Tell us exactly what input you type in. 3) Tell us what you saw happen, and what you think should have happened.
Avoid using system calls in your program. system("PAUSE") is certainly less than ideal. Using a call to system creates a subprocess, which on windows is fairly expensive and in any case not terribly cheap on any operating system.
Too vague, and Walt's rationale (from the link) is largely moot:
"It's not portable." The system() function is inherently non-portable because its argument is dependent on available system console commands. Though it's wise to acknowledge this when choosing to use it, I wouldn't claim portability as a reason to avoid something unless there's an equally good and portable solution. Walt's stated solution is the portable way to simulate the behavior of system("PAUSE"), but it's not equally good because you have to consider extraneous characters in the input stream.
"It's a very expensive and resource heavy function call." That's easily the dumbest reason for avoiding system("PAUSE") if you take half a second to think about what system("PAUSE") does. As an argument against system() in general it's appropriate, but not for system("PAUSE") specifically.
"You must include a header you probably don't need: stdlib.h or cstdlib" Oh no, you must include a standard header that contains commonly used functions and types. The horror! ;) Who is Walt to say that the header isn't needed for other things? Further, if you choose to use the system() function then that header is needed anyway, so it's not really an argument against system(), it's just fluff to make the short list longer.
I'd say avoid using the system() function in favor of a system call that you know won't execute a malicious program of the same name. Walt doesn't address this at all, but it's by far the most persuasive argument against the system() funciton. The problem with stuff like system("PAUSE") is I could easily write a malicious program, call it PAUSE.exe, and put it in a place that ensures your code will run it. Your code will run it with whatever permissions the user running your program has, which could be devastating if you have root permissions.
The problem with system() is that it's inherently insecure. That alone is the only reason you need to avoid it.