If you mean when writing in the forums, that is (or was) a known and expected situation -- due to those characters being markdown characters and being "interpreted" instead of displayed "as entered". Though I think @ianmorland was intending to fix this.
If *#10# appears correctly (and it does in my preview), that fix is at least partially implemented already. Though it might only work for new posts?
Do you have a specific shortcode code that still exhibits the problem? If you do, you might have to "spell it out" (like asterisk hash 10 hash) so we can understand your example -- or post it as a quote by putting it at the beginning of a line with > in front of it.