Unfortunately there are many such tools that rather than use read access they open a file or registry key with write permissions and it is that which is being blocked, the potential to modify avast files or registry entries (rather than an actual attack).
Personally I wouldn't be worrying about them as the entries in the log show that those attempts have been blocked.
For instance if I open one of the protected logs with a text editor other than notepad it will try to open with write permission and this is blocked.
19/01/2010 22:40:38 Write access to file \Device\HarddiskVolume1\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\log\selfdef.log denied. [C:\Program Files\JGsoft\EditPadLite\EditPadLite.exe]
This was me just opening the selfdef.log to see what it had in it some time ago (I have .log files set to be opened with editpad lite)
Many registry scanners do the same thing when seeking out redundant registry keys they are opened with write permission.
24/01/2010 01:14:42 Write access to registry key \REGISTRY\MACHINE\SYSTEM\CurrentControlSet\Services\aswUpdSv\ denied. [E:\Utilities-Non-Registry\~\RegSeeker\RS1-55\RegSeeker.exe]