If this is a stop and search at something like an airport... random numbers between 1 and 10, as in... somewhere between, and including, the next 1st to the next 10th, would be unmanageable. The inspectors, and the inspection area, would be back-logged in no time!
How about something like... two clocks... one running at a normal rate (system clock), and one running at a variable-random rate?
The variable-random rate clock could change rates, at anytime, based on events... such as someone walking through the entry barrier. This would require a roll-yer-own clock with a specified-variable rate. The rate is likely to change... but maybe not. The rate would change, between 1 and 10, on any entry, based on Alaric's scheme. The variable-rate clock would be no slower than the real-rate clock.
This would produce two separate waves... one being a real-time based sine-wave, the other being a random-time based sine-wave. Where the random time-base is equal to, or greater than, the real time-base.
Then, when the milli-second (or second) values of each clock coincided, or were within a particular range of each other... that range possibly being defined, or random by the same method, then... on the next entry, no matter how long before that next entry, turn on the RED light for inspection. (Damn... I hate these inspections!)
Methods can be applied to allow for tuning the system to provide adequate strip-searching without overloading the inspection process room.
Don't forget to throw in a "random" setting that will allow an inspector to get a coke and a smoke, now and then.