Ah, ok. Well 4RAM is the memory for the C139 communications chip, which often fails and isn't used. The fact yours says 00000002 doesn't mean a lot - it's a totally duff RAM chip, but it isn't used by Assault so that's not the problem.
As a brief show-and-tell.
mame -debug.
Load Rolling Thunder 2 as that actually shows you the memory tests, whereas Assault does them silently. Both have the same memory locations though.
Hit F8 repeatedly to advance the game one frame at a time until it says 4RAM Test.
Now hold F11 to slowly go through instructions and you'll see it's changing Register A1 and it's got a number in the 0x480000's
View attachment 35811
If you look at namcos2.cpp, you'll see that's the 'sci' RAM
View attachment 35810
Which, if you read around that file, you'll see that's the serial communications.
Now if you go to debug and open a memory window and type in 0x480000, and keep pressing F11, you'll see it's changing all the 00's to FF's in that area as part of a memory test.
Type some crap into the FFs.
View attachment 35812
Press F5 to run the game
And it's not happy:
View attachment 35813
Now you could go and do the same to break Assault by putting a watchpoint in the SCI memory region ('wpset 0x480000,0x1000,rw' in the console), running until it pauses, then mashing the address, but I'll leave that unless someone needs a further tutorial. I did do it though:
View attachment 35814
So that's not your sprite problem.