Sorry, NY Eve's party, I understood your question in a different way than you thought. Every file from the certain archive is unpacked, scanned, deleted (temp or unallocated) and then avast seeks to the next file in the archive (this works for all archives except those four ones written above). The whole file has to be unpacked and then scanned (it's not possible to scan the file during unpacking). Avast can't scan a file, e.g. If you didn't have space to unpack 300Mb setup.exe.
Hey, keep up the good party
But back to business, does this mean you cannot scan files that will not fit into memory?
I was hoping that the stream of data coming from a file on disk or in memory could be changed into a stream of data coming from the unpacker and thus enabling scanning archives with large files on systems with small disks.
I am not talking about performance in this case, that's not the problem.