	Netwatch Performance Issues

1.0	When NETWATCH starts, it will be slightly slower than when it
	gets rolling, since each host involves a NAME SERVER lookup
	to resolve addresses.
	NOTE: Version 0.7 has attempted to address this by making a
		service process (netresolv) take care of this lookup.
		It appears to be much more efficient.

2.0	On slow machines, you may find it sluggish due to the linked 
	list requirement of insertions and updating. Each host is
	looked up linearly within the list. (Yes... this is an
	issued which needs to be addressed... but not right now)

3.0	As of Version 0.8a, NETWATCH will take the time to sort for
	High usage hosts on 30 sec. intervals. It works fine for me
	but it has the potential to be a bottleneck for slower systems.

