SLC Ground Controller described runway incursion event; indicating instructions issued were not in accordance with 7110.65; reporter claiming use of 7110.65 phraseology has contributed to past incursion mishaps.

Narrative

I was working the Ground Control East position. Due to the weather and runway use plan we were departing all turn departures off of Runway 16R. I issued taxi instructions to Aircraft Y to taxi via K; hold short Runway 17 at K5. The read back was full and correct. I then was scanning the east side taxiways trying to pick the aircraft up visually. I then noticed an ASDE-X target moving towards the runway at K2 without a Data Block. I went over to the Local East Controller; and pointed out the aircraft; who then canceled the takeoff clearance of Aircraft X that was on departure roll. I issued instructions for the Aircraft Y to exit the runway; which he did. He then complied with all other instructions and departed without incident. Recommendation; issued phraseology not in accordance with the 7110.65. I issued 'taxi via K hold short Runway 17 at K5 and expect Runway 16R for departure'. I did this because I have issued the instruction per the 7110.65 and had numerous problems in this same area; including several runway incursions. I was intending to give this aircraft progressive instructions. I believe that in circumstances such as this that there needs to some latitude for ground controllers to use more effective phraseology when controlling aircraft near trouble spots.